|
|
3.3 | Troubleshooting Routing Protocols | ||
| 3.3.1 | Routing protocol troubleshooting process |
|
All routing protocol troubleshooting should begin with a logical
sequence, or process flow. This process flow is not a rigid outline
for troubleshooting an internetwork. However, it is a foundation from
which a network administrator can build a problem-solving process to
suit a particular environment.
Cisco routers provide numerous integrated commands to assist in monitoring and troubleshooting an internetwork:
Cisco IOS show commands are among the most important tools for understanding the status of a router, detecting neighboring routers, monitoring the network in general, and isolating problems in the network. EXEC debug commands can provide a wealth of information about interface traffic, internal error messages, protocol-specific diagnostic packets, and other useful troubleshooting data. Use debug commands to isolate problems, not to monitor normal network operation. Only use debug commands to look for specific types of traffic or problems. Before using the debug command, narrow the problems to a likely subset of causes. Use the show debugging command to view which debugging features are enabled.
|